…1214)

* fix(core): drop api_format from Azure targets; surface pi-ai errors

Two regressions from the Vercel AI SDK → pi-ai migration (#1206) broke
Azure evals end-to-end whenever a target had api_format=chat (or unset
on a config still defaulting to it):

1. The migration kept the api_format field but pi-ai's azure-openai-
   responses provider always hits /openai/v1/responses. With chat-style
   defaults still in place, AgentV sent ?api-version=2024-12-01-preview
   to the Responses path, which Azure rejects with 400 "API version
   not supported." Every eval call failed.

2. invokePiAi never inspected pi-ai's stopReason. When pi-ai surfaced
   the 400 as { stopReason: 'error', errorMessage: '...', content: [] },
   the adapter happily returned an empty assistant message, which
   downstream graders then reported as "Unexpected EOF" JSON parse
   failures — completely hiding the underlying HTTP error.

Fix:
- Remove api_format from Azure targets entirely. Pi-ai's adapter only
  exposes the Responses path, so a chat/responses switch on this
  provider has no effect. Default Azure api version to v1 (matching the
  /openai/v1/responses path). Reject api_format on Azure targets at both
  validation and resolution time with a migration message pointing at
  `provider: openai` for chat-completions-only deployments. api_format
  remains supported on `provider: openai`.
- Throw from invokePiAi when pi-ai returns stopReason 'error' so failures
  reach the surface and withRetry can apply its status-based retry
  policy. The thrown message includes the parsed HTTP status so
  isRetryableError can decide correctly.

Also drops api_format from the repo's .agentv/targets.yaml and updates
the Azure provider docs to document the migration path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore: biome formatter pass on self-update files

Pure whitespace fix from `biome format --write` on apps/cli/src/self-update.ts
and apps/cli/test/self-update.test.ts. Pre-existing issue from #1213; the
pre-push hook fails on these files independently of any other change, so
fixing them here unblocks the bug-fix branch's push.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>